Method and system for reporting message disposition in a communication network

ABSTRACT

Methods, servers and mobile stations are provided to allow a sender mobile station which has transmitted a message toward a recipient mobile station via a first protocol to be notified that the message has been delivered to the recipient mobile station via a different protocol. The sender mobile station may be notified that the message was delivered to the recipient mobile station via a different protocol method via a disposition notification message comprising an indication that the message was delivered to the recipient mobile station via a different protocol.

RELATED APPLICATIONS

The present application is a continuation application of U.S. patent application Ser. No. 15/119,826; entitled “METHOD AND SYSTEM FOR REPORTING MESSAGE DISPOSITION IN A COMMUNICATION NETWORK”; which is a National Stage Entry of International Patent Application No. PCT/IB2016/052957; entitled “METHOD AND SYSTEM FOR REPORTING MESSAGE DISPOSITION IN A COMMUNICATION NETWORK”; and filed at the World Intellectual Property Organization on May 19, 2016; which claims the priority of U.S. Provisional Patent Application No. 62/163,797; entitled “METHOD AND SYSTEM FOR REPORTING MESSAGE DISPOSITION IN A COMMUNICATION NETWORK”; and filed at the United States Patent and Trademark Office on May 19, 2015. The content of all previous applications in incorporated herein by reference.

TECHNICAL FIELD

The present description generally relates to messaging in communication networks, and more particularly relates to notification of message disposition in communication networks.

BACKGROUND

Various messaging technologies can be employed today for delivering messages between mobile stations in a communication network. One of the most widely used messaging technologies is Short Message Service which is commonly known as SMS. SMS messages are usually transmitted over circuit-switched communication networks.

With the advent of packet-switched radio access network such as General Packet Radio Service (GPRS) network and more recently, Long Term Evolution (LTE) network, new forms of messaging services have become available. One of them is Instant Messaging (IM) service which is supported, for instance, by IP Multimedia Subsystem (IMS) networks. IMS is a framework which has been developed by the 3rd Generation Partnership Project (3GPP) to provide Internet-based services over packet-switched radio access networks such as GPRS, LTE and WiFi.

Packet-switched radio access networks are now deployed alongside legacy circuit-switched radio access networks. As such, mobile stations are now most often capable of accessing both circuit-switched networks and packet-switched networks. Hence, it is not uncommon for such mobile stations to now support SMS messaging, IM messaging, or both.

Sometimes however, a standalone message, a chat, a group chat or a file transfer request (e.g. an IM message) may need to be interworked to a legacy SMS messaging technology (e.g. as an SMS message) when the recipient mobile station is a mobile station which only supports SMS services (e.g. a legacy mobile station). Interworking of an IM message to an SMS message may also be needed during roaming scenarios during which the recipient mobile station is out of IMS coverage. In such scenario, the recipient would normally be able to receive the IM message but being unable to access the packet-switched radio access network, the recipient mobile station falls back to the circuit-switched radio access network over which only SMS messages can be received.

Still, current IM services supported by packet-switched networks such as IMS networks offer the possibility for the sender to be notified when the transmitted IM messages are delivered or read. For instance, RFC 5438—Instant Message Disposition Notification, provides a framework for such notifications. Most IM services may also provide the IM message sender an indication of the active typing from the recipient, thereby allowing the IM message sender to know that it should expect a reply. Such a feature has been described in RFC 3994—Indication of Message Composition for Instant Messaging.

As communication networks now support many types of mobile stations, some of them capable of receiving various types of messages while others limited to IM messages or SMS messages, mechanisms have been developed and put in place to allow an IM message to be interworked to an SMS message when the recipient is only capable of receiving SMS messages (e.g. the recipient uses a legacy mobile station or is out of IMS coverage). Similarly, an SMS message may also be interworked to an IM message if the recipient is limited to receiving IM messages.

However, when an IM message sent by a sender needs to be interworked due to the fact that the recipient is either using a legacy mobile station or is out of IMS coverage, most, if not all, the advanced notification functionalities, e.g. disposition notification, indication of message composition, etc., provided by the IM service are lost. Hence, when interworking between an IM message and a SMS message is performed, the sender of the IM message has no way of knowing that some of the advanced notification functionalities will not be available for the given message exchange or chat session.

For the sender, there is a perceived service loss and service inconsistency which may negatively affect the overall IM service experience. Still, it remains that setting proper user expectations is an important service aspect for network operators.

Therefore, it would be desirable to provide method and system that obviate or mitigate the above described problems.

SUMMARY

In accordance with the present description, methods and systems are provided to allow the sender of a message to be notified of the delivery of the message to the intended recipient via a protocol which may not support advanced disposition notification features. Consequently, the sender of the message will be able to adjust its expectations of the messaging experience with the recipient.

In a first exemplary embodiment, a method of operating a messaging application server generally comprises receiving a message originating from a sender mobile station, the message being addressed to a recipient mobile station, the message being received via a first protocol, determining that the recipient mobile station is not operative to receive the message via the first protocol, responsive to determining that the recipient mobile station is not operative to receive the message via the first protocol, converting the message into a format compliant with a second protocol different from the first protocol, wherein the recipient mobile station is operative to receive the converted message via the second protocol, transmitting the converted message toward the recipient mobile station via the second protocol, receiving a notification message comprising an indication that the converted message was delivered to the recipient mobile station, generating a disposition notification message comprising an indication that the message was delivered to the recipient mobile station via a different protocol, and transmitting the disposition notification message toward the sender mobile station via the first protocol.

In some embodiments, determining that the recipient mobile station is not operative to receive the message via the first protocol may comprise determining that the recipient mobile station is not configured, or does not have the capability, to receive the message via the first protocol.

In some embodiments, determining that the recipient mobile station is not operative to receive the message via the first protocol may comprise determining that the recipient mobile station is not within coverage of a communication network supporting the first protocol.

In some embodiments, determining that the recipient mobile station is not operative to receive the message via the first protocol may comprise receiving an error message comprising an indication that the recipient mobile station is not operative to receive the message via the first protocol.

In some embodiments, forwarding the converted message toward the recipient mobile station may comprise transmitting the converted message toward a communication network supporting the second protocol. In such embodiments, receiving a notification message comprising an indication that the converted message was delivered to the recipient mobile station may comprise receiving the notification message from the communication network.

In some embodiments, the message transmitted by the sender mobile station may be an Instant Messaging (IM) message, and the disposition notification message may be an Instant Message Disposition Notification, IMDN, message. In such embodiments, the IMDN message may comprise an element (e.g. status element) populated with a predetermined value (e.g. a predetermined sub-element). In some embodiments, the predetermined value may be indicative of a type of technology and/or of a type of network and/or of a type of protocol used to deliver the message to the recipient mobile station.

In some embodiments, the disposition notification message may be a delivery notification message, a processing notification message, or a display notification message.

In some embodiments, the first protocol is a packet-switched based protocol and the second protocol is a circuit-switched based protocol.

In some embodiments, the first protocol used by the sender mobile station to transmit the message may be the Session Initiation Protocol, SIP.

In some embodiments, the second protocol used to deliver the message to the recipient mobile station may be the Mobile Application Part (MAP) of the Signal System 7 (SS7) circuit-switched protocol.

In some embodiments, the second protocol used to deliver the message to the recipient mobile station may be a communication protocol supporting email services (e.g. Internet Message Access Protocol (IMAP), Post Office Protocol 3 (POP3), etc.).

In a second exemplary embodiment, a messaging application server configured to perform one or more messaging application server functionalities as described herein may comprise one or more communication interfaces configured to communicate (e.g. receive messages from and transmit messages to) with a first communication network (e.g. a packet-switched network such as an IP Multimedia Subsystem (IMS) network), and configured to communicate (e.g. receive messages from and transmit messages to) with a second communication network (e.g. a circuit-switched network such as a Public Land Mobile Network (PLMN)), and circuitry operatively connected to the communication interface(s), the circuitry being configured for performing messaging application server functionalities as described herein.

In some embodiments, the circuitry may comprise a processor and a memory having stored therein computer-readable instructions which when executed by the processor, allow the messaging application server to perform messaging application server functionalities as described herein. In some embodiments, the processor may be implemented as general purpose processing circuitry (e.g. processor, microprocessor, central processing unit, microcontroller, etc.), special purpose processing circuitry (e.g. application specific integrated circuits (ASIC), field programmable gate arrays (FPGA), etc.), or as a combination of both.

In a third exemplary embodiment, a messaging application server configured to perform one or more messaging application server functionalities as described herein may comprise a message receiving module configured to receive a message originating from a sender mobile station, the message being addressed to a recipient mobile station, the message being received via a first protocol, a determining module configured to determine that the recipient mobile station is not operative to receive the message via the first protocol, a converting module configured to convert the message into a format compliant with a second protocol different from the first protocol in response to the determining module determining that the recipient mobile station is not operative to receive the message via the first protocol, wherein the recipient mobile station is operative to receive the converted message via the second protocol, a converted message transmitting module configured to transmit the converted message toward the recipient mobile station via the second protocol, a notification message receiving module configured to receive a notification message comprising an indication that the converted message was delivered to the recipient mobile station, a disposition notification message generating module configured to generate a disposition notification message comprising an indication that the message was delivered to the recipient mobile station via a different protocol, and a disposition notification message transmitting module configured to transmit the disposition notification message toward the sender mobile station via the first protocol.

In a fourth exemplary embodiment, a method of operating a mobile station generally comprises transmitting a message toward a recipient mobile station via a first protocol, and receiving a disposition notification message in response to the transmitted message, the disposition notification message comprising an indication that the message was delivered to the recipient mobile station via a different protocol. The method may also comprise generating a user notification in response to receiving the disposition notification message comprising the indication that the message was delivered to the recipient mobile station via a different protocol.

In some embodiments, the method may comprise transmitting the message to a packet-switched network (e.g. an IP Multimedia Subsystem (IMS) network), and receiving the disposition notification message from the packet-switched network (e.g. the IMS network).

In some embodiments, the message transmitted by the mobile station may be an Instant Messaging (IM) message, and the disposition notification message may be an Instant Message Disposition Notification, IMDN, message. In such embodiments, the IMDN message may comprise an element (e.g. a status element) populated with a predetermined value (e.g. a predetermined sub-element). In some embodiments, the predetermined value may be indicative of a type of technology and/or of a type of network and/or of a type of protocol used to deliver the message to the recipient mobile station.

In some embodiments, the disposition notification message may be a delivery notification message, a processing notification message, or a display notification message.

In some embodiments, the protocol used by the mobile station to transmit the message is a packet-switched based protocol. In some embodiments, the protocol may be the Session Initiation Protocol, SIP.

In some embodiments, the protocol used to deliver the message to the recipient mobile station is a circuit-switched based protocol. In some embodiments, the protocol may be the Mobile Application Part (MAP) of the Signal System 7 (SS7) circuit-switched protocol.

In some embodiments, the protocol used to deliver the message to the recipient mobile station may be a communication protocol supporting email services (e.g. Internet Message Access Protocol (IMAP), Post Office Protocol 3 (POP3), etc.).

In a fifth exemplary embodiment, a mobile station configured to perform one or more mobile station functionalities as described herein may comprise a communication interface configured to communicate (e.g. receive messages from and transmit messages to) with a communication network (e.g. a packet-switched network such as an IMS network), and circuitry operatively connected to the communication interface, the circuitry being configured for performing mobile station functionalities as described herein.

In some embodiments, the circuitry may comprise a processor and a memory having stored therein computer-readable instructions which when executed by the processor, allow the mobile station to perform one or more mobile station functionalities as described herein. In some embodiments, the processor may be implemented as general purpose processing circuitry (e.g. processor, microprocessor, central processing unit, microcontroller, etc.), special purpose processing circuitry (e.g. application specific integrated circuits (ASIC), field programmable gate arrays (FPGA), etc.), or as a combination of both.

In a sixth exemplary embodiment, a mobile station configured to perform one or more mobile station functionalities as described herein may comprise a message transmitting module configured to transmit a message toward a recipient mobile station via a first protocol, and a disposition notification message receiving module configured to receive a disposition notification message in response to the transmitted message, the disposition notification message comprising an indication that the message was delivered to the recipient mobile station via a different protocol. The mobile station may also comprise a user notification generating module configured to generate a user notification in response to the disposition notification message receiving module receiving the disposition notification message.

Other aspects and features will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments in conjunction with the accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described, by way of example only, with reference to the attached figures, wherein:

FIG. 1 is a schematic diagram of a simplified network architecture in accordance with some embodiments.

FIG. 2 is a signaling diagram of a first exemplary scenario in accordance with some embodiments.

FIG. 3 is a signaling diagram of a second exemplary scenario in accordance with some embodiments.

FIG. 4 is a flow chart of a method performed at a messaging application server in accordance with some embodiments.

FIG. 5 is a flow chart of a method performed at a mobile station in accordance with some embodiments.

FIG. 6 is a block diagram of a messaging application server in accordance with some embodiments.

FIG. 7 is another block diagram of a messaging application server in accordance with some embodiments.

FIG. 8 is a block diagram of a mobile station in accordance with some embodiments.

FIG. 9 is another block diagram of a mobile station in accordance with some embodiments.

DETAILED DESCRIPTION

The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the description and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the description. In the following description, numerous specific details are set forth. However, it is understood that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail in order not to obscure the understanding of the description. Those of ordinary skill in the art, with the included description, will be able to implement appropriate functionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

Referring first to FIG. 1, an exemplary and simplified network architecture 100 allowing messaging interworking is illustrated. The network architecture 100 generally comprises an IMS core network 102, a public land mobile network (PLMN) 104, and a messaging application server 106 which comprises the necessary interworking functionalities or modules (e.g. IP-Short-Message-Gateway (IP-SM-GW), Interworking Selection Function (ISF), etc.) to interwork messages exchanged between the IMS core network 102 and the PLMN 104.

As depicted in FIG. 1, the IMS core network 102 can be accessed over a packet-switched radio access network (RAN) 108 such as an evolved universal terrestrial radio access network (EUTRAN) compliant with the LTE standards. For its part, the PLMN 104 can be accessed over a circuit-switched radio access network (RAN) 110.

During normal operations of the network architecture 100, an IMS-enabled mobile station 112 can establish a Session Initiation Protocol (SIP) session with the IMS core network 102 in order for the mobile station 112 to be able to transmit and receive IMS-compliant messages, i.e. Instant Messaging (IM) messages, to and from the IMS core network 102. The IMS core network 102 is generally responsible for forwarding the IM messages to the appropriate IMS-enabled recipient mobile station according to the IMS framework.

However, on some occasions, the subscriber of the sender mobile station 112 may wish to send an IM message to a recipient mobile station which is not operative to receive IM messages.

In some cases, the recipient mobile station which is not operative to receive IM messages could be an IMS-enabled mobile station, such as mobile station 114 in FIG. 1, which is unable to access the IMS core network 102. For instance, mobile station 114 could be outside the coverage of a packet-switched RAN such as packet-switched RAN 108 and thus outside of IMS coverage.

In other cases, the recipient mobile station could be a non-IMS-enabled mobile station (e.g. a legacy mobile station) such as mobile station 116 in FIG. 1. Such a mobile station 116 would be unable to receive IM messages.

Messaging applications running on IMS-enabled mobile stations such as mobile station 112 are generally provided with additional features. For instance, such applications may indicate if the IM message sent by the subscriber was properly delivered to the recipient mobile station. To allow such notification to be done, Instant Message Disposition Notification (IMDN) messages (e.g. as defined in RFC 5438, incorporated herein by reference) are generated by the IMS core network 102 and transmitted back to the sender mobile station.

However, when an IMS-enabled sender mobile station transmits an IM message toward a mobile station which is either outside of IMS coverage (e.g. mobile station 114 in FIG. 1) or non-IMS-enabled (e.g. mobile station 116 in FIG. 1), the messaging application server must interwork the IM message, that is convert or otherwise translate the IM message into a Short Message Service (SMS) message or a Multimedia Messaging Service (MMS) message, before forwarding it to the recipient mobile station 114 or 116 via the PLMN 104.

It will be appreciated that when an IM message is interworked by the messaging application server, the sending subscriber has no way to know whether the IM message was delivered properly. Hence, in accordance with the present description, the messaging application server is configured to populate the IMDN message it generates in response to the delivery of an IM message via interworking with an indication that the IM message was delivered to the recipient mobile station via a different protocol. As such, the sending subscriber will know that the mobile station of the recipient subscriber does not support the additional disposition notification capabilities and thus, the sending subscriber will not expect such disposition notifications.

FIG. 2 illustrates an exemplary signaling diagram of a scenario 200 in which an IM message is interworked into an SMS or an MMS message (hereafter, SMS/MMS message) by the messaging application server 106.

At S202, the IMS-enabled mobile station 112 sends an IM message, addressed to the IMS-enabled recipient mobile station 114, to the IMS core network 102. This IM message may be transmitted via Session Initiation Protocol (SIP) (i.e. a first protocol). Upon receiving the IM message, the IMS core network 102 tries to forward, at S204, the IM message to the recipient mobile station 114 according to normal IMS procedure. Upon failing to deliver the IM message to the recipient mobile station 114 according to normal IMS procedure, the IMS core network 102 notifies, at S206, the messaging application server 106 of an error in trying to deliver the IM message. The error notification transmitted by the IMS core network 102 to the messaging application server 106 may comprise an indication that the IMS-enabled recipient mobile station 114 is not IMS-registered (e.g. out of IMS coverage).

After receiving the error notification from the IMS core network 102, the messaging application server 106 determines, at S208, that the recipient mobile station 114 is not operative to receive the IM message via IMS. Upon making this determination, the messaging application server 106 converts, or otherwise translates, at S210, the IM message into an SMS/MMS message.

At S212, the messaging application server 106 then forwards the interworked IM message, now as an SMS/MMS message, to the PLMN 104, which further delivers, at S214, the SMS/MMS message to the recipient mobile station 114 via the circuit-switched RAN 110.

Upon receiving the SMS/MMS message, the recipient mobile station 114 transmits, at S216, a SMS/MMS delivered message (e.g. a Submit report) to the PLMN 104 which further forwards it to the messaging application server 106 at S218.

After receiving the SMS/MMS delivered message, the messaging application server 106 generates, at S220, an IMDN message comprising an indication that the IM message was delivered to the recipient mobile station 114 albeit via a different protocol (e.g. via a legacy network). The messaging application server 106 then transmits the IMDN message to the IMS core network 102, at S222, which further forwards it to the sender mobile station 112, at S224, via the packet-switched RAN 108.

FIG. 3 illustrates an exemplary signaling diagram of another scenario in which an IM message is interworked into an SMS/MMS message by the messaging application server 106. Scenario 300 is similar to scenario 200 and as such, only the differing steps will be described.

In scenario 300, the recipient mobile station 116 is not IMS-enabled, in contrast to scenario 200 in which the recipient mobile station 114 was IMS-enabled but outside of IMS coverage and thus unreachable via the IMS core network 102. Hence, in scenario 300, the error message returned by the IMS core network 102 to the messaging application server 106, at S226, upon failing to forward the IM message to the recipient mobile station 116 may comprise an indication that the recipient mobile station 116 is not IMS-enabled (e.g. the recipient mobile station 116 is a legacy mobile station).

From the point of view of the sender mobile station 112 and of the messaging application server 106, both scenarios 200, 300 are essentially identical. Indeed, for the sender mobile station 112, whether the recipient mobile station is IMS-enabled (e.g. mobile station 114) but out of IMS coverage or simply not IMS-enabled (e.g. mobile station 116), the IMDN message that the sender mobile station 112 will receive will indicate, in both cases, that the IM message was delivered via a different protocol (e.g. via a legacy network). Likewise, for messaging application server 106, once it has determined that the recipient mobile station is not operative to receive the IM message (i.e. step S208), the messaging application server 106 will convert, or otherwise translate, the IM message into an SMS/MMS message and forward it to the PLMN 104 for delivery to the recipient mobile station via the legacy network.

In some embodiments, the IMDN message generated by the messaging application server 106 can be one of a delivery notification message, a processing notification message, and a display notification message. Notably, the particular type of IMDN message generated by the messaging application server 106 can be requested in the IM message sent by the sender mobile station 112. For instance, the IM message sent by the sender mobile station 112 could comprise an indication of a request to receive a delivery IMDN message.

IMDN messages generally comprise a status element which can be populated with predetermined values, each indicative of particular disposition status. However, the status element of different types of IMDN messages may carry different predetermined values. For instance, in an IMDN message indicating delivery, the status element may carry one of the following sub-elements: <delivered>, <failed>, <forbidden>, or <error>. For IMDN message indicating processing, the status element may carry one of the following sub-elements: <processed>, <stored>, <forbidden>, or <error>. Finally, for IMDN message indicating display, the status element may carry one of the following sub-elements: <displayed>, <forbidden>, or <error>.

It will be appreciated that the status sub-elements <delivered> and <failed> (for delivery IMDN messages), <processed> and <stored> (for processing IMDN messages), and <displayed> (for display IMDN messages) are self-explanatory. With respect to the <forbidden> sub-element and <error> sub-element, they generally respectively indicate that the disposition was denied and that an internal server error has occurred.

In order to notify the sender mobile station 112 that the IM message was delivered via a different protocol, e.g. a legacy network supporting a different protocol, IMDN messages may need to carry information reflective of the technology used to deliver the original message.

In some embodiments, this information can be carried as a new sub-element of the status element of the IMDN message. This additional sub-element may indicate, for instance, that the IM message was disposed of via a protocol different from SIP and which is not IMS compliant. In some embodiments, this additional sub-element may generically be identified as <legacy-messaging>. Understandably, in other embodiments, this additional sub-element could have a different name, e.g. <legacy-network>, <legacy-SMS>, <legacy-MMS>, <legacy-email>, etc. reflective of the legacy nature of the delivery technology.

In other embodiments, this information can be carried as an IMDN message indicating interworking, e.g. an interworking notification message. As the other IMDN messages, the status of this IMDN message could include one or more sub-elements, including the new sub-elements such as <legacy-SMS>, <legacy-MMS>, <legacy-email>, etc. listed above, reflective of the technology used to deliver the original message.

In addition, in some embodiments, more than one predetermined value could be used to populate the status element of the IMDN message. For instance, if it is desired to make a distinction between an IM message delivered as an SMS message and an IM message delivered as an MMS message, the status element of the IMDN message could be populated with <legacy-SMS> when an IM message is delivered as an SMS message, or with <legacy-MMS> when an IM message is delivered as an MMS message.

Notably, when the sender mobile station receives an IMDN message with its status element populated with the sub-element <legacy-messaging>, or any other equivalent sub-element, or an interworking IMDN message, the messaging application which has sent the IM message for which the IMDN message is received can process the IMDN message accordingly. For instance, the messaging application can provide an indication, e.g. a visual indication, that the IM message sent by the sender mobile station has been delivered, or otherwise disposed of, albeit via a different protocol (e.g. different from SIP) and which does not support advanced disposition notifications. As such, the user of the sender mobile station 112 can be made aware that it should not expect advanced disposition notifications (e.g. display notifications) or indications of the other party typing a message, for the current message exchange with the user of the recipient mobile station 114 or 116. By making the user of the sender mobile station 112 aware that it should not expect advanced disposition notifications or message composing indications from the other party, the user of the sender mobile station is less likely to be disappointed by the lack of richer features naturally present with the first protocol, in the current message exchange.

It will be appreciated that for the IMS-enabled mobile station 112 to receive an IMDN message, it typically needs to include a request to that effect in the transmitted IM message. In embodiments where the indication of interworking of the message to a legacy messaging technology is captured via a new sub-element (e.g. <interworking-notification>) of the existing disposition notification types (e.g. delivery, processing, display), the IMS-enabled mobile station 112 may list one or more of the new sub-element values (e.g. <legacy-sms>, etc.), or a generic “interworking” value, for which it requests to receive a notification. For instance, under the procedure described in RFC5438, the IMS-enabled mobile station 112 may add a generic “interworking” value, alongside the existing “positive-delivery” and “negative-delivery” values, in the header of the IM message, to receive notification of interworking. In embodiments where the indication of interworking of the message to a legacy messaging technology is captured via a new type of disposition notification (e.g. interworking IMDN message), the IMS-enabled mobile station 112 may simply list it as a top level notification type “interworking” (e.g. as specified in RFC5438 for the “display” and “processing” notifications).

Turning now to FIG. 4, an embodiment of a method of operating the messaging application server 106 is illustrated. The messaging application server 106 first receives a message (e.g. an IM message) originating from a sender mobile station and addressed to a recipient mobile station (step S402). The message is received via a first protocol (e.g. SIP). Then, the messaging application server 106 determines that the recipient mobile station to which the message is addressed is not operative to receive the message via the first protocol (step S404). As indicated above, it can be that the recipient mobile station is IMS-enabled, and should normally be able to receive the IM message, but is currently out of IMS coverage and as such, cannot receive the IM message. In other words, the IM message cannot be routed to the recipient mobile station via IMS. It can also be that the recipient mobile station is not IMS-enabled since it is, for instance, a legacy mobile station. Once the messaging application server 106 has determined that the recipient mobile station 114 or 116 is not operative to receive the message via the first protocol, the messaging application server 106 converts, or otherwise translates, the message into a message (e.g. an SMS/MMS message) compliant with a second protocol (e.g. MAP SS7 protocol) (step S406). Once the message has been converted into a converted message, the messaging application server 106 transmits the converted message toward the recipient mobile station (step S408), via the second protocol.

Then, the messaging application server 106 receives a notification message (e.g. a SMS/MMS delivered message) indicating that the converted message has been delivered to the recipient mobile station (step S410). In response to the reception of this notification message, the messaging application server 106 then generates a disposition notification message (e.g. an IMDN message) comprising an indication that the message was delivered via a different protocol (step S412). Finally, the messaging application server 106 transmits the generated disposition notification message towards the sender mobile station (step S414).

In some embodiments, the messaging application server 106 may determine that the recipient mobile station is not operative to receive the message via the first protocol upon receiving an error message from the network (e.g. IMS core network) through which the message has been received. In some embodiments, the messaging application server 106 may determine itself that the recipient mobile station is not operative to receive the message via the first protocol.

Referring now to FIG. 5, an embodiment of a method of operating a mobile station is illustrated. The method starts with the mobile station sending a message (e.g. an IM message) addressed to a recipient mobile station (step S502), the message being sent via a first protocol (e.g. SIP). Then, the mobile station receives a disposition notification message (e.g. an IMDN message) comprising an indication that the message was delivered to the recipient mobile station but via a different protocol (step S504).

In some embodiments, upon receiving the disposition notification message comprising the indication that the message was delivered to the recipient mobile station via a different protocol, the mobile station may generate a user notification (e.g. a visual notification) to notify the subscriber of the mobile station, or otherwise make the subscriber aware, that the message was delivered to the recipient mobile station via a different protocol (step S506). In some embodiments, the notification may comprise an indication (e.g. a message) displayed by the mobile station. In some embodiments, the user notification may comprise the use of a different color.

FIG. 6 illustrates an embodiment of a messaging application server 106 adapted for use in one or more of the described embodiments. The messaging application server 106 comprises one or more communication interfaces 602 configured to communicate (e.g. receive messages from and transmit messages to) with a first communication network (e.g. an IMS network), and configured to communicate (e.g. receive messages from and transmit messages to) with a second communication network (e.g. a PLMN), and circuitry 604 operatively connected to the communication interface(s) 602, the circuit being configured for performing messaging application server functionalities as described herein.

In some embodiments, the circuitry 604 may comprise a processor 606 and a memory 608 having stored therein computer-readable instructions which when executed by the processor 606, allow the messaging application server 106 to perform messaging application server functionalities as described herein.

In some embodiments, the processor 606 may be implemented as general purpose processing circuitry (e.g. processor, microprocessor, central processing unit, microcontroller, etc.), special purpose processing circuitry (e.g. application specific integrated circuits (ASIC), field programmable gate arrays (FPGA), etc.), or as a combination of both.

FIG. 7 shows another embodiment of a messaging application server 106 adapted for use in one or more of the described embodiments. In the embodiment of FIG. 7, the messaging application server 106 comprises a message receiving module 702 configured to receive a message (e.g. an IM message) originating from a sender mobile station, the message being addressed to a recipient mobile station, the message being received via a first protocol (e.g. SIP). The messaging application server 106 also comprises a determining module 704 configured to determine that the recipient mobile station is not operative to receive the message via the first protocol, and a converting module 706 configured to convert the message into a format compliant with a second protocol (e.g. MAP SS7) different from the first protocol in response to the determining module 704 determining that the recipient mobile station is not operative to receive the message via the first protocol. Understandably, it will be appreciated that the recipient mobile station is operative to receive the converted message (e.g. an SMS/MMS message) via the second protocol. The messaging application server 106 also comprises a converted message transmitting module 708 configured to transmit the converted message toward the recipient mobile station via the second protocol, and a notification message receiving module 710 configured to receive a notification message comprising an indication that the converted message was delivered to the recipient mobile station. The messaging application server 106 also comprises a disposition notification message generating module 712 configured to generate a disposition notification message (e.g. an IMDN message) comprising an indication that the message sent by the sender mobile station was delivered to the recipient mobile station via a different protocol, and a disposition notification message transmitting module 714 configured to transmit the disposition notification message toward the sender mobile station via the first protocol.

FIG. 8 illustrates an embodiment of a mobile station 112 adapted for use in the above exemplary embodiments. The mobile station 112 comprises a communication interface 802 configured to communicate (e.g. receive messages from and transmit messages to) with a communication network (e.g. IMS network), and circuitry 804 operatively connected to the communication interface 802. The circuitry 804 is generally responsible for controlling the operations of the mobile station 112.

In some embodiments, the circuitry 804 may comprise a processor 806 and a memory 808 having stored therein computer-readable instructions which when executed by the processor 806, allow the mobile station to perform mobile station functionalities as described herein. In some embodiments, the processor 806 may be implemented as general purpose processing circuitry (e.g. processor, microprocessor, central processing unit, microcontroller, etc.), special purpose processing circuitry (e.g. application specific integrated circuits (ASIC), field programmable gate arrays (FPGA), etc.), or as a combination of both.

FIG. 9 illustrates another embodiment of a mobile station 112 adapted for use in the above exemplary embodiments. The mobile station 112 comprises a message transmitting module 902 configured to transmit a message (e.g. an IM message) toward a recipient mobile station via a first protocol, and a disposition notification message receiving module configured to receive a disposition notification message (e.g. an IMDN message) in response to the transmitted message, the disposition notification message comprising an indication that the transmitted message was delivered to the recipient mobile station via a different protocol. The mobile station 112 may also comprise a user notification generating module 906 configured to generate a user notification in response to the disposition notification message receiving module receiving the disposition notification message.

Some embodiments may be represented as a non-transitory software product stored in a machine-readable medium (also referred to as a computer-readable medium, a processor-readable medium, or a computer usable medium having a computer readable program code embodied therein). The machine-readable medium may be any suitable tangible medium including a magnetic, optical, or electrical storage medium including a diskette, compact disk read only memory (CD-ROM), digital versatile disc read only memory (DVD-ROM) memory device (volatile or non-volatile), or similar storage mechanism. The machine-readable medium may contain various sets of instructions, code sequences, configuration information, or other data, which, when executed, cause a processor to perform steps in a method according to one or more of the described embodiments. Those of ordinary skill in the art will appreciate that other instructions and operations necessary to implement the described embodiments may also be stored on the machine-readable medium. Software running from the machine-readable medium may interface with circuitry to perform the described tasks.

The above-described embodiments are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the description. 

1) A method of operating a mobile station, the method comprising: transmitting an Instant Messaging, IM, message toward a recipient mobile station; receiving an Instant Message Disposition Notification, IMDN, message in response to the transmitted IM message, the IMDN message comprising a status element populated with a sub-element indicating that the IM message was delivered to the recipient mobile station as a Short Message Service, SMS, message or as a Multimedia Messaging Service, MMS, message; and generating a user notification in response to receiving the IMDN message. 2) The method as claimed in claim 1, wherein the generated user notification visually indicates that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message. 3) The method as claimed in claim 2, wherein the generated user notification visually indicates that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message by displaying the generated user notification using a different color. 4) The method as claimed in claim 1, wherein the sub-element indicating that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message indicates <legacy-SMS> or <legacy-MMS>. 5) The method as claimed in claim 1, wherein the IMDN message is one of a delivery IMDN message, a display IMDN message, an interworking IMDN message, and a processing IMDN message. 6) A mobile station, the mobile station comprising a processor and a memory storing instructions which, when executed by the processor, configure the mobile station to: transmit an Instant Messaging, IM, message toward a recipient mobile station; receive an Instant Message Disposition Notification, IMDN, message in response to the transmitted IM message, the IMDN message comprising a status element populated with a sub-element indicating that the IM message was delivered to the recipient mobile station as a Short Message Service, SMS, message or as a Multimedia Messaging Service, MMS, message; and generate a user notification in response to receiving the IMDN message. 7) The mobile station as claimed in claim 6, wherein the generated user notification visually indicates that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message. 8) The mobile station as claimed in claim 7, wherein the generated user notification visually indicates that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message by displaying the generated user notification using a different color. 9) The mobile station as claimed in claim 6, wherein the sub-element indicating that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message indicates <legacy-SMS> or <legacy-MMS>. 10) The mobile station as claimed in claim 6, wherein the IMDN message is one of a delivery IMDN message, a display IMDN message, an interworking IMDN message, and a processing IMDN message. 11) A method of operating a messaging application server, the method comprising: receiving an Instant Messaging, IM, message originating from a sender mobile station, the IM message being addressed to a recipient mobile station; responsive to determining that the recipient mobile station is not operative to receive IM messages, converting the received IM message into a Short Message Service, SMS, message or a Multimedia Messaging Service, MMS, message; transmitting the SMS message or the MMS message toward the recipient mobile station; receiving a notification message comprising an indication that the SMS message or the MMS message was delivered to the recipient mobile station; generating an Instant Message Disposition Notification, IMDN, message comprising a status element populated with a sub-element indicating that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message; and transmitting the IMDN message toward the sender mobile station. 12) The method as claimed in claim 11, wherein determining that the recipient mobile station is not operative to receive IM messages comprises determining that the recipient mobile station is not configured to receive IM messages. 13) The method as claimed in claim 11, wherein determining that the recipient mobile station is not operative to receive IM messages comprises receiving an error message comprising an indication that the recipient mobile station is not operative to receive IM messages. 14) The method as claimed in claim 11, wherein the sub-element indicating that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message indicates <legacy-SMS> or <legacy-MMS>. 15) The method as claimed in claim 11, wherein the IMDN message is one of a delivery IMDN message, a display IMDN message, an interworking IMDN message, and a processing IMDN message. 16) A messaging application server, the messaging application server comprising a processor and a memory storing instructions which, when executed by the processor, configure the messaging application server to: receive an Instant Messaging, IM, message originating from a sender mobile station, the IM message being addressed to a recipient mobile station; responsive to determining that the recipient mobile station is not operative to receive IM messages, convert the received IM message into a Short Message Service, SMS, message or a Multimedia Messaging Service, MMS, message; transmit the SMS message or the MMS message toward the recipient mobile station; receive a notification message comprising an indication that the SMS message or the MMS message was delivered to the recipient mobile station; generate an Instant Message Disposition Notification, IMDN, message comprising a status element populated with a sub-element indicating that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message; and transmit the IMDN message toward the sender mobile station. 17) The messaging application server as claimed in claim 16, wherein when determining that the recipient mobile station is not operative to receive IM messages, the messaging application server is further configured to determine that the recipient mobile station is not configured to receive IM messages. 18) The messaging application server as claimed in claim 16, wherein when determining that the recipient mobile station is not operative to receive IM messages, the messaging application server is further configured to receive an error message comprising an indication that the recipient mobile station is not operative to receive IM messages. 19) The messaging application server as claimed in claim 16, wherein the sub-element indicating that the IM message was delivered to the recipient mobile station as an SMS message or as an MMS message indicates <legacy-SMS> or <legacy-MMS>. 20) The messaging application server as claimed in claim 16, wherein the IMDN message is one of a delivery IMDN message, a display IMDN message, an interworking IMDN message, and a processing IMDN message. 